Techniques for storing data on message queuing middleware servers without registration of the sending application

ABSTRACT

A lightweight store and forward architecture allows packets of data to be forwarded from an application running on a client system to a server system. An application that generates information in response to an event or other condition assembles a packet that includes a target identifier and data to be sent to the target. The packet is stored in a file in the client system. A messaging client forwards packets form the file to a messaging server on a target server system. The messaging server dispatches the information to a messaging handler to process the information. Thus, the application generating the packet is not required to handle network communications related to the packet and registration of a target application is not required.

FIELD OF THE INVENTION

[0001] The invention relates to network communications. Morespecifically, the invention relates to techniques for storing data on amiddleware server.

BACKGROUND OF THE INVENTION

[0002] Store and forward message systems are commonly used for manyapplications, for example, electronic mail. Commercially available storeand forward software applications include Message Queue Server fromMicrosoft Corporation of Redmond, Washington and the MQSeries ofproducts available from International Business Machines of Armonk, N.Y.

[0003] These store and forward applications typically operate by anapplication that is sending a message establishing a connection with aserver or other device that is to receive the message. These types ofstore and forward applications require substantial network, disk andmemory resources. One reasons that the network, disk and memoryresources are consumed by store and forward applications is that acomplete application program interface (API) is included in eachapplication that provides store and forward functionality.

[0004] The store and forward application API is typically afull-function API that provides a specific method prescribed by acomputer operating system or by another application program by which aprogrammer writing an application program can make requests of theoperating system or another application. The full-function API allows anapplication to provide store and forward functionality. However, in somesituations a full-function store and forward API requires anunnecessarily large portion of available resources.

BRIEF DESCRIPTION OF THE DRAWINGS

[0005] The invention is illustrated by way of example, and not by way oflimitation, in the figures of the accompanying drawings in which likereference numerals refer to similar elements.

[0006]FIG. 1 is a conceptual illustration of one embodiment of a clientand server coupled to provide a lightweight store and forward messagequeuing architecture.

[0007]FIG. 2 is a block diagram of an electronic system.

[0008]FIG. 3 is a flow diagram of one embodiment of lightweight storeand forward message queuing.

DETAILED DESCRIPTION

[0009] Techniques for storing data on message queuing middleware serverswithout registration of the sending application are described. In thefollowing description, for purposes of explanation, numerous specificdetails are set forth in order to provide a thorough understanding ofthe invention. It will be apparent, however, to one skilled in the artthat the invention can be practiced without these specific details. Inother instances, structures and devices are shown in block diagram formin order to avoid obscuring the invention.

[0010] Reference in the specification to “one embodiment” or “anembodiment” means that a particular feature, structure, orcharacteristic described in connection with the embodiment is includedin at least one embodiment of the invention. The appearances of thephrase “in one embodiment” in various places in the specification arenot necessarily all referring to the same embodiment.

[0011] A lightweight store and forward architecture allows packets ofdata to be forwarded from an application running on a client system to aserver system. An application that generates information in response toan event or other condition assembles a packet that includes a targetidentifier and data to be sent to the target. The packet is stored in afile in the client system. A messaging client forwards packets form thefile to a messaging server on a target server system. The messagingserver dispatches the information to a messaging handler to process theinformation. Thus, the application generating the packet is not requiredto handle network communications related to the packet and registrationof a target application is not required.

[0012] Lightweight store and forward messaging is particularly useful insituations where small messages are passed in a single direction (e.g.,client to server). For example, in a network of electronic devices(e.g., computer systems, printers, facsimile machines) particularoperating events may be of interest to a remote management device. Inresponse to one of these events, the networked devices can generatepackets that include event information that are forwarded to themanaging device. The managing device can respond to the events inresponse to receiving the packets identifying and/or describing theevents. Lightweight store and forward messaging can be used in othersituations or can be used in a bidirectional manner.

[0013]FIG. 1 is a conceptual illustration of one embodiment of a clientand server coupled to provide a lightweight store and forward messagequeuing architecture. FIG. 1 illustrates a single application running onclient 100; however, any number of applications can run on client 100and forward messages in a similar manner.

[0014] Client 100 can be any type of electronic system, for example, acomputer system, a set top box, a personal digital assistant (PDA).Similarly, server 150 can also be any type of electronic system. A blockdiagram of an electronic system is described below with respect to FIG.2.

[0015] Client 100 includes messaging (MSG) enabled application 110. MSGenabled application can be any type of application that supports storeand forward messaging as described herein. Client 100 also includes MSGfile 120 and MSG client 130. Server 150 includes MSG server 150 and MSGhandler 170. MSG enabled application 110, MSG file 120, MSG client 130,MSG server and MSG handler 170 can be implemented as any combination ofhardware and/or software in any manner known in the art.

[0016] When MSG enabled application 110 generates information that is tobe sent to server 150, the information is encoded as a packet and thepacket is stored in MSG file 120. The information stored in the packetcan represent any type of electronic information. For example, executionerrors or other events can generate a packet of information describingthe nature and/or consequences of the event.

[0017] In one embodiment, MSG enabled application 110 acquires exclusiveaccess to MSG file 120 for purposes of writing the packet to MSG file120. After the packet is written the MSG file 120, the exclusive accessis relinquished. In one embodiment, the packet takes the following form:TABLE 1 MSG packet format Parameter Format Target ID 32-bit unsignedinteger Length 16-bit unsigned integer Packet Data Variable lengthbinary data

[0018] In the embodiment of Table 1, the TargetID is a 32-bit value thatrepresents the ultimate target of the packet. In alternate embodiments adifferent length value can be used as the TargetID. In the embodiment ofTable 1, the Length is a 16-bit value representing the length, in bytes,of the data carried by the packet. Use of a 16-bit length value limitsthe packet data length to 65,535 bytes. In alternate embodiments adifferent value can be used to designate the packet data length if adifferent packet length limit is desired. Packet data represents theinformation carried by the packet.

[0019] MSG client 130 forwards packets stored in MSG file 120 to MSGserver 160. In one embodiment, packets are forwarded using TCP/IP;however, any appropriate protocol known in the art can be used. BecauseMSG client 130 handles forwarding of packets, MSG enabled application110 is required only to assemble packets and store the packets in MSGfile 120. MSG client 130 coordinates network communications. This freesMSG enabled application 110 to continue execution without beingconstrained by network communications.

[0020] Additional advantages of the client side architecture of FIG. 1is that the API included in MSG enabled application 110 is smaller andless complex that an API required for traditional store and forwardmessaging and the ultimate target of the packet is not required to beregistered with the application that generates the target.

[0021] When a network connection is established between MSG client 130and MSG server 160, MSG client 130 forwards the packet from MSG file120. Upon receiving the packet, MSG server 160 dispatches theinformation stored in the packet to MSG registered handler 170. MultipleMSG handlers can exist to process different types of information orevents that are stored in packets. In one embodiment, MSG handler 170 isa dynamic linked library (DLL) that is loaded based on a TargetID of apacket. The DLL then processes the packet data. Other techniques forprocessing the packet data can also be used.

[0022] When the packet data is dispatched to MSG handler 170, MSG server160 sends an acknowledge (ACK) message to MSG client 130 identifying thepacket that has been dispatched. Upon receipt of the ACK message MSGclient 130 drops the packet from MSG file 120. In one embodiment, thedispatched packet is replaced by a null packet in MSG file 120 and,periodically, null packets are removed and the memory reclaimed.Dropping packets from MSG file 120 can be accomplished by othertechniques as well.

[0023]FIG. 2 is a block diagram of an electronic system. The electronicsystem illustrated in FIG. 2 is intended to represent a range ofelectronic systems, for example, computer systems, set top boxes, PDAs.Alternative electronic systems can include more, fewer and/or differentcomponents.

[0024] Electronic system 200 includes bus 201 or other communicationdevice to communicate information, and processor 202 coupled to bus 201to process information. While electronic system 200 is illustrated witha single processor, electronic system 200 can include multipleprocessors and/or co-processors. Electronic system 200 further includesrandom access memory (RAM) or other dynamic storage device 204 (referredto as main memory), coupled to bus 201 to store information andinstructions to be executed by processor 202. Main memory 204 also canbe used to store temporary variables or other intermediate informationduring execution of instructions by processor 202.

[0025] Electronic system 200 also includes read only memory (ROM) and/orother static storage device 206 coupled to bus 201 to store staticinformation and instructions for processor 202. Data storage device 207is coupled to bus 201 to store information and instructions. Datastorage device 207 such as a magnetic disk or optical disc andcorresponding drive can be coupled to electronic system 200.

[0026] Electronic system 200 can also be coupled via bus 201 to displaydevice 221, such as a cathode ray tube (CRT) or liquid crystal display(LCD), to display information to a computer user. Alphanumeric inputdevice 222, including alphanumeric and other keys, is typically coupledto bus 201 to communicate information and command selections toprocessor 202. Another type of user input device is cursor control 223,such as a mouse, a trackball, or cursor direction keys to communicatedirection information and command selections to processor 202 and tocontrol cursor movement on display 221. Electronic system 200 furtherincludes network interface 230 to provide access to a network, such as alocal area network.

[0027] Instructions are provided to memory from a storage device, suchas magnetic disk, a read-only memory (ROM) integrated circuit, CD-ROM,DVD, via a remote connection (e.g., over a network via network interface230) that is either wired or wireless, etc. In alternative embodiments,hard-wired circuitry can be used in place of or in combination withsoftware instructions to implement the present invention. Thus, thepresent invention is not limited to any specific combination of hardwarecircuitry and software instructions.

[0028] A machine-accessible medium includes any mechanism that provides(i.e., stores and/or transmits) information in a form readable by amachine (e.g., a computer). For example, a machine-accessible mediumincludes read only memory (ROM); random access memory (RAM); magneticdisk storage media; optical storage media; flash memory devices;electrical, optical, acoustical or other form of propagated signals(e.g., carrier waves, infrared signals, digital signals); etc.

[0029]FIG. 3 is a flow diagram of one embodiment of lightweight storeand forward message queuing. The flow of FIG. 3 is described withrespect to an event; however, messages can be generated in response toany type of condition. Events are detected at 310. In one embodiment,events are predetermined operating conditions; however, any type ofcondition can be detected at 310.

[0030] A packet is generated in response to the event at 320. In oneembodiment, the packet is generated by an application that detects theevent. In an alternate embodiment, an application can detect the evenand cause another application (e.g., an operating system) to generatethe packet.

[0031] The packet is forwarded to a MSG file at 330. In one embodiment,the application generating the packet stores the packet in the MSG fileand continues operation, if possible. Because the application is onlystores the packet in the MSG file on the same electronic device as theapplication is running, the API for message forwarding that is includedin the application is much smaller than a full function store andforward API.

[0032] A messaging client application monitors the MSG file for additionof new packets and, at 340, forwards the packet(s) to a messagingserver. The messaging client handles all network communications thusrelieving the application of network communications related to the eventthat has been detected. The messaging server receives the packet formthe messaging client via a network connection.

[0033] The messaging server dispatches the event to a messaging handlerat 350. The messaging handler processes the information included in thepacket that is related to the detected event to cause the serverelectronic system to take a predetermined action. In one embodiment themessaging handler is a DLL that is invoked in response to apredetermined TargetID carried by a packet. In alternate embodiments,the packet can be processed in a different manner.

[0034] At 360, the messaging server generates an acknowledge message inresponse to dispatching the packet to the messaging handler. Themessaging client drops the packet from the MSG file, at 370, in responseto the acknowledge message from the messaging server.

[0035] In the foregoing specification, the invention has been describedwith reference to specific embodiments thereof. It will, however, beevident that various modifications and changes can be made theretowithout departing from the broader spirit and scope of the invention.The specification and drawings are, accordingly, to be regarded in anillustrative rather than a restrictive sense.

What is claimed is:
 1. A method comprising: generating a packet in response to a predetermined event; storing the packet locally; forwarding the packet with a client messaging application to a server messaging application via a network connection managed by the client messaging application; and dispatching the packet with the server messaging application to a messaging handler that processes the packet.
 2. The method of claim 1 wherein the packet includes a target identifier and a variable length data field.
 3. The method of claim 2 wherein the messaging server application selects a messaging handler from a plurality of messaging handlers based on the target identifier.
 4. The method of claim 1 further comprising: generating an acknowledge message in response to the packet being dispatched to the messaging handler; and communicating the acknowledge message from the messaging server application to the messaging client application.
 5. The method of claim 4 wherein further comprising dropping the packet from the local storage in response to the acknowledge message being received by the messaging client application.
 6. An article comprising a machine-accessible medium to provide machine-readable instructions that, when executed, cause one or more electronic systems to: generate a packet in response to a predetermined event; store the packet locally; forward the packet with a client messaging application to a server messaging application via a network connection managed by the client messaging application; and dispatch the packet with the server messaging application to a messaging handler that processes the packet.
 7. The article of claim 6 wherein the packet includes a target identifier and a variable length data field.
 8. The article of claim 7 wherein the messaging server application selects a messaging handler from a plurality of messaging handlers based on the target identifier.
 9. The article of claim 6 further comprising sequences of instructions that, when executed, cause the one or more electronic systems to: generate an acknowledge message in response to the packet being dispatched to the messaging handler; and communicate the acknowledge message from the messaging server application to the messaging client application.
 10. The article of claim 9 wherein further comprising sequences of instructions that, when executed, cause the one or more electronic systems to drop the packet from the local storage in response to the acknowledge message being received by the messaging client application.
 11. A computer data signal embodied in a data communications medium shared among a plurality of network devices comprising sequences of instructions that, when executed, cause one or more electronic systems to: generate a packet in response to a predetermined event; store the packet locally; forward the packet with a client messaging application to a server messaging application via a network connection managed by the client messaging application; and dispatch the packet with the server messaging application to a messaging handler that processes the packet.
 12. The computer data signal of claim 11 wherein the packet includes a target identifier and a variable length data field.
 13. The computer data signal of claim 12 wherein the messaging server application selects a messaging handler from a plurality of messaging handlers based on the target identifier.
 14. The computer data signal of claim 11 further comprising sequences of instructions that, when executed, cause the one or more electronic systems to: generate an acknowledge message in response to the packet being dispatched to the messaging handler; and communicate the acknowledge message from the messaging server application to the messaging client application.
 15. The computer data signal of claim 14 wherein further comprising sequences of instructions that, when executed, cause the one or more electronic systems to drop the packet from the local storage in response to the acknowledge message being received by the messaging client application.
 16. A network architecture comprising: a client electronic system having one or more processors to run one or more programs and a memory system coupled to the processor, the memory system to store one or more message packets, wherein the one or more processors also runs a messaging client that forwards message packets stored in the memory system; and a server electronic system coupled to the client electronic system, the server electronic system having one or more processors to run one or more programs in a memory system coupled to the processor, wherein the one or more processors runs a messaging server that receives forwarded messages from the messaging client and processes the messages in a predetermined manner.
 17. The network architecture of claim 16 further comprising a second client electronic system having one or more processors to run one or more programs and a memory system coupled to the processor, the memory system to store one or more message packets, wherein the one or more processors also runs a messaging client that forwards message packets stored in the memory system, and further wherein the one or more processors runs a messaging server that receives forwarded messages from the messaging client of the second client electronic system and processes the messages in a predetermined manner. 